release: v0.1.1210 - #3452
Merged
Merged
Conversation
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe package version and exported ChangesRelease version alignment
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts v0.1.1210.
Ships #3450 - a host can now publish adapter-only connectors it drives with its own client.
Hiding those connectors from every lookup removed the connector definitions out from under hosts that implement the adapter. veryfront-api ships a Salesforce client and names salesforce in its promoted set, but since v0.1.1209
getConnector('salesforce')returned undefined, so tool names stopped resolving and OAuth connection binding stopped being required. The integration stayed connectable with no working tools.The scaffolding guard does not move.
veryfront init, the template loader and the MCP catalog tools keep refusing these connectors, because generated routes run on the generic OAuth runtime and that is exactly what cannot serve them. TheOAuthProviderconstructor guard onruntimeSupport: "provider-adapter-required"is untouched. Those CLI tests pass unmodified in #3450, which is the evidence the seam is in the right place.Catalog lookup was the part that was too narrow.
getConnector,listConnectorsandgetIconnow useisCatalogVisibleIntegration, which additionally honours a newVERYFRONT_HOST_ADAPTER_INTEGRATIONSenv var. Hosts name each connector they actually implement; blanket values are ignored, so a sweep can never widen the scaffolding surface by accident.Same three files as every release bump:
deno.json,src/utils/version-constant.ts, and the regenerated hydration runtime.After this publishes
Nothing changes for any consumer until it opts in. veryfront-api will set
VERYFRONT_HOST_ADAPTER_INTEGRATIONS=salesforceand restore its catalog expectations, which is what puts Salesforce back in the Studio integration list with working tools. The other 11 adapter-only connectors stay hidden everywhere until some host declares an adapter for them.Summary by CodeRabbit